home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
tex-k-archive.gz
/
tex-k-archive
/
000154_kb@cs.umb.edu_Mon Jan 10 12:24:02 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-11
|
1KB
Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA05887
(5.65c/IDA-1.4.4 for <tex-k@CS.UMB.EDU>); Tue, 11 Jan 1994 08:55:33 -0500
Received: by terminus.cs.umb.edu id AA08146
(5.65c/IDA-1.4.4 for tex-k@CS.UMB.EDU); Mon, 10 Jan 1994 17:24:02 -0500
Date: Mon, 10 Jan 1994 17:24:02 -0500
From: "K. Berry" <kb@cs.umb.edu>
Message-Id: <199401102224.AA08146@terminus.cs.umb.edu>
To: Enrique_Ibarra-Anaya@VOLGA.EDRC.CMU.EDU, karl@cs.umb.edu
Subject: Re: Problems compiling dvips
Cc: tex-k@CS.UMB.EDU
/bin/ld: Unsatisfied symbols:
assert (code)
I don't know why this could be happening.
The way to find out where assert is being referenced is to run nm on all
the .o files in kpathsea and look for references to assert.
<assert.h> is included in kpathsea/c-std.h (if HAVE_ASSERT_H is
defined), so it should be included in all the source files you mention.
I suppose I should just remove all the references to assert in the
sources. Heaven forbid we be able to do runtime checks on our code!